Skip to content

Conversation

@juan518munoz
Copy link
Collaborator

@juan518munoz juan518munoz commented Dec 23, 2025

Blocked: depends on a miden-base dep with

Closes #1381

@SantiagoPittella SantiagoPittella force-pushed the jmunoz-note-screener-cleanup branch from e800bdb to d7795cb Compare January 9, 2026 18:44
@SantiagoPittella SantiagoPittella marked this pull request as ready for review January 9, 2026 18:47
/// Returns the block number at which the note can be consumed.
/// Returns None if the note is already consumable or never possible
#[wasm_bindgen(js_name = "consumableAfterBlock")]
pub fn consumable_after_block(&self) -> Option<u32> {
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe we should return BlockNumber here

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Might be wrong, but I think that we are using u32 to send block numbers in the web client, right?

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, I don't think there is a BlockNumber JS model struct. Maybe we can add one but it doesn't seem too critical.

Copy link
Collaborator

@fkrause98 fkrause98 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

looks good, should we also add tests for the web client exposed models?

@igamigo igamigo merged commit 9af41f7 into next Jan 14, 2026
29 checks passed
@igamigo igamigo deleted the jmunoz-note-screener-cleanup branch January 14, 2026 21:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Refactor NoteScreener API

5 participants